Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Benefits and constraints on mapping fields

The most common reason for mapping fields is to enable Progress Dynamics to link the correct field from the SDO with a linked field on the viewer required for dynamic lookups. You can have the fields mapped automatically by specifying fields from the data source on the viewer as the linked fields in the lookup. In cases where you cannot do this, you can explicitly map the fields to ensure that the linked fields are populated with the correct value.

For field mapping to work, you must map all of the fields in the dynamic lookup to the viewer SDO. For more information, see the "Using mapped fields" section.

Progress Dynamics does not support field mapping for viewers using a SmartBusinessObject (SBO) as their data source.

Note: Adding joins to an SDO in order to make fields available for a dynamic lookup as part of the standard SDO data retrieval does not always provide a performance benefit. The expense of the extra join, plus the extra data returned, might cancel any benefit that might be gained were the fields already available in the SDO without the join. You must assess the trade-off individually for each case.